Channel Import Settings
Prefer port names
This option forces TPT to use MATLAB's port name as signal names. It works only on scalar signals.
Natively use bus/enumeration/fixed-point data types specified by SUT
If the check box is selected,
- custom data types specified by the SUT will be used directly
The S-function will output the data with these data types. No further conversions is needed. Signals with Simulink.Bus objects as data type will be channels with struct data types in TPT. - array signals with Simulink.Bus objects as data type are supported
- the S-function will act as a single function call source and triggers function calls directly based on a trigger-semantic
This means that function calls are always executed at each sample where the value changed betweentrue
andfalse
. At the first cycle the function call will be executed if the value differs from the initial value.
Although allowed in MATLAB, TPT cannot distinguish between signals sharing the same name. When Concatenate signal names is selected, TPT will name all TPT signals with their respective bus hierarchy in MATLAB. For example, if the signal passes through several buses, the bus element myBus.fooAndBar.foo
will be imported as myBus_fooAndBar_foo
.
Always
TPT concatenates all signals in all buses.
Never
TPT does not concatenate any signal in any bus.
When necessary
Only if two different signals in two different buses have the same name, TPT automatically concatenates them.
Treat vectors as
Vector signals can be imported from MATLAB and treated as a single vector signal, or as multiple scalar signals.
Vector start index
A vector of size n
generates n
signals in TPT. While importing the interface, the names of the signals are formed with the name of the vector and the addition of _xxx
to it, where xxx
is the index of the element in the vector.
As some tools start internal calculation from 0 and others from 1, it is possible to choose 0 or 1 as the initial number for vector indexing to increase compatibility.